Appmaker notes

Back to index


This document relates to the AppMaker program on Macintosh and how OOFILE applications can be automatically generated. This first version assumes you are generating code for the PowerPlant framework.

The basic philosophy is to make things as simple as possible for someone to construct an application. They should have to enter a minimal amount of code.

Please read gui.txt for an outline of the OOFILE gui integration philosophy. The following assumes you know how we handle browsing and editing data.

LIMITATIONS OF THIS RELEASE

This beta version has a few limitations, that will be rapidly fixed:
- no easy linking of fields, views and lists - you have to type in the names
- specifying additional indexes
- specifying relationships between tables
- specifying embedded tables (eg: Locations)
- editing report-writer layouts

GETTING STARTED

You define your database by adding at least one dbTable category. Within the dbTable you specify the persistent fields.

You must also add a dbView category - this will be used by the ListControl on the Browser window. When you type in the names in the dbView's fields, be very careful to match the spelling from the dbTable.

You must now set the following Properties by clicking on each Category (eg: a Dialog and pressing command-I for Info). Nearly all the Properties are popup menus so very easy to set.

Document
- dbBrowseWindow
- dbAddDialog
- dbEditDialog
- itsTable

Window
- OOFILEview (leave at None for non-OOFILE window)

Dialog
- editsTable (leave at None for non-OOFILE dialog)

Edit Text
- linkedField (again, be careful with your spelling when you type this in)

List
- itsView

CODE THAT APPMAKER GENERATES


Back to index